Atomic notes are small, single-purpose notes that each capture one idea clearly enough that it can be reused elsewhere.

They’re the building blocks of a Zettelkasten-style system: instead of writing one giant “everything note,” you create many focused notes and connect them with links.

What makes a note “atomic”

An atomic note should:

• Express one idea (one concept, claim, method, pattern, definition, question)
• Stand on its own without requiring surrounding context
• Be linkable (it should naturally connect to other notes)
• Be reusable (you can reference it from multiple places without rewriting it)
• Be written in your own words (even if it cites sources)

If a note contains multiple ideas, it’s probably a hub / map note (MoC) or it should be split.

Why atomic notes work

Atomic notes make knowledge easier to maintain and grow:

• You can compose larger documents from smaller parts
• You can update a single concept in one place and improve everything that references it
• You can discover relationships by linking ideas across topics
• You reduce “note bloat” by avoiding repeated explanations everywhere

Atomic notes are how “learning” turns into a connected system instead of a pile of pages.

How I write atomic notes

My default pattern:

1. Name the note after the idea, not the project
   Example: “Precision vs Recall” instead of “Week 3 Notes”
2. Write a 1–3 sentence core definition at the top
3. Add just enough detail to be useful later
4. Add links to related notes (parents, children, siblings)
5. Add a source section if it’s grounded in a book/paper/article
6. If the note grows into a list of many ideas, I convert it into a Map of Content and split the concepts out

A simple template

Here’s the shape I aim for:

• Definition / claim (what it is)
• Why it matters (when you’d use it)
• Example (small, concrete)
• Links (related concepts)
• Sources (optional)

Examples

Atomic note: “Knowledge graphs”
One clear definition + a short example + links to “Graph databases,” “Semantic search,” “Obsidian graph,” “D3 visualization.”

Not atomic: “My entire PKM system”
That’s a high-level hub and should be broken into atomic notes like:

• “Capture workflow”
• “Atomic notes”
• “Maps of Content”
• “Tagging vs linking”
• “Spaced repetition”

Common failure modes

• Notes that are actually journaling (time-based, not idea-based)
• Notes that are too big (multiple unrelated sections)
• Notes that are too thin (a title and a single vague sentence)
• Notes with no links (they don’t participate in the graph)

Atomic notes are small, but not empty.

Information